failover$504823$ - translation to italian
DICLIB.COM
AI-based language tools
Enter a word or phrase in any language 👆
Language:     

Translation and analysis of words by artificial intelligence

On this page you can get a detailed analysis of a word or phrase, produced by the best artificial intelligence technology to date:

  • how the word is used
  • frequency of use
  • it is used more often in oral or written speech
  • word translation options
  • usage examples (several phrases with translation)
  • etymology

failover$504823$ - translation to italian

ACTIVITY TO EVALUATE HOW WELL AN APPLICATION IS ABLE TO RECOVER FROM CRASHES, HARDWARE FAILURES AND OTHER SIMILAR PROBLEMS
Failover Testing

failover      
n. eccedenza su una rete informatica per assicurare il massimo della disponibilità su rete dopo un caso di cedimento di una componente dell"hardware (inform.)

Definition

failover
<reliability> Automatically switching to a different, redundant system upon failure or abnormal termination of the currently active system. Failover can be applied to a cluster of servers, to network or storage components or any other set of redundant devices that must provide {high availability} because down-time would be expensive or inconvenient. It may be implemented in hardware, software or a combination. A "hot standby" is continuously active at the same time as the failed system, using some kind of load balancing to share the work, whereas a "warm standby" is ready to become active at short notice. When the failed system is operational again it may "failback", i.e. become (one of) the active system(s) or it may become a warm standby. (2008-01-15)

Wikipedia

Recovery testing

In software testing, recovery testing is the activity of testing how well an application is able to recover from crashes, hardware failures and other similar problems.

Recovery testing is the forced failure of the software in a variety of ways to verify that recovery is properly performed. Recovery testing should not be confused with reliability testing, which tries to discover the specific point at which failure occurs. Recovery testing is basically done in order to check how fast and better the application can recover against any type of crash or hardware failure etc. Recovery testing is simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times). Type or extent of recovery is specified in the requirement specifications. It is basically testing how well a system recovers from crashes, hardware failures, or other catastrophic problems

Examples of recovery testing:

  1. While an application is running, suddenly restart the computer, and afterwards check the validness of the application's data integrity.
  2. While an application is receiving data from a network, unplug the connecting cable. After some time, plug the cable back in and analyze the application's ability to continue receiving data from the point at which the network connection disappeared.